home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Visual Basic Controls
/
Visual Basic Controls.iso
/
vbcontrol
/
remdatab
/
readme.txt
< prev
next >
Wrap
Text File
|
1999-08-17
|
6KB
|
158 lines
RemoteDataBar v1.1
==================
Overview
--------
RemoteDataBar is an ActiveX control that lets applications access data
stored in a remote OLE DB (ADO) data source. It allows you to bind
controls at design time (or run time) to a data source "over the web".
The protocols supported are HTTP, HTTPS, and DCOM. Compared to other
data source objects that either require a direct database connection
over a local network (and consume expensive database resources), can
only be bound to controls on an HTML page, or require extensive
client-side setup, RemoteDataBar is simple to install and use, has
sophisticated multi-user features, and is highly scalable in an
enterprise environment.
An associated ActiveX DLL provides unbound access to data through ADO
recordsets, SQL queries, and stored procedures.
Built upon Microsoft's distributed computing technologies, these
components are ideal to use from any environment that supports ActiveX
controls, such as Visual Basic.
Release Notes
-------------
v1.1.3 (17 August 1999)
Resolved issues
---------------
Data Access Objects server
- UpdateBatchConf did not update non-conflicting records if any
conflicts occurred
RemoteDataBar
- Error message was displayed when trying to add records to an
empty recordset (problem introduced in v1.1.2)
- Save and Cancel Changes buttons displayed error message if the
recordset was empty (problem introduced in v1.1.2)
- Enabled properties of navigation buttons were not set properly
when Add and Save buttons were pressed
v1.1.2 (11 August 1999)
Resolved issues
---------------
Data Access Objects server
- UpdateBatchConf sometimes raised an "Errors occurred" error
from the server and did not return a conflict recordset
RemoteDataBar
- Enabled properties of Next, Last buttons were not set properly
when Add followed by Cancel Changes was pressed
- BeforeInsert event was firing prematurely when new record added
to empty Recordset
- BeforeInsert event was firing when calling Recordset's
UpdateBatch method after calling RemoteDataBar's
UpdateBatch[Conf] method
- BeforeInsert event was not firing when RemoteDataBar's
UpdateBatch[Conf] method was called if Save button (method) not
pressed (called) after adding a new record
- Errors messages were shown in some of the public methods when
errors occurred, instead of errors being raised
- DeleteRecord, UpdateBatch[Conf] methods were raising "Object
variable or With Block variable not set" error if the Recordset
property was Nothing
- When UpdateType was set to UpdateTypeCurrent, the first change
to a field was immediately saved into the database
- Changing a record for the first time caused it to be updated in
the database before Save button (method) was pressed (called)
- A newly added record in UpdateTypeBatch could only be deleted
using the "Cancel Changes" button rather than the Delete button
(which was disabled)
New behaviour:
- "Cancel Changes" is disabled for a newly added record. To
delete the record, use the Delete button.
- The UndoRecord method now has no effect on a newly added
record. Instead, use the DeleteRecord method.
Issues to be resolved
---------------------
- UpdateBatchConf does not show database errors, so it is hard to
determine whether, for example, a delete was successful
v1.1.1 (21 July 1999)
Data Access Objects server
- Fixed error when stored procedure returns null values in
output parameters
v1.1.0 (18 July 1999)
Data Access Objects client
- Added GetRSMultiple method, InternetTimeout property
RemoteDataBar
- Added FirstRecord, PreviousRecord, NextRecord, LastRecord,
AddRecord, SaveRecord, DeleteRecord, UndoRecord methods
Requirements
------------
Server
MS Windows 95/98/NT
MS Transaction Server
MS Internet Information Server 4.0 or Personal Web Server 4.0
(if HTTP or HTTPS will be used)
MDAC 2.0 or later (available from
http://www.microsoft.com/data/download.htm)
Client
MS Windows 95/98/NT
MDAC 2.0 or later client components (included with
Internet Explorer 5.0; otherwise you'll need to download it
from http://www.microsoft.com/data/download.htm and install
on the clients)
Development Environment
-----------------------
RemoteDataBar has been tested in Visual Basic versions 5 and 6, and with
Oracle 7.3, Oracle 8, MS Access 97, and MS SQL Server 7.0 databases.
Installation Notes
------------------
Run Server.exe to extract the server setup files on the server machine.
Then run setup.exe to install the required server components.
Run Client.exe to extract the client setup files on the client machine.
Then run setup.exe to install the client components. CAB files will be
made available shortly for distribution of the client components via
internet download.
Behavioural issues pertaining to disconnected recordsets in general
-------------------------------------------------------------------
- Delete followed by an error leaves the record deleted in the local
Recordset, but not in the database. Because the user is working with a
disconnected recordset, the record *must* be deleted locally and
submitted for update, regardless of whether the update succeeds or
fails. For total control over this behaviour, use the DAO Client
component instead of RemoteDataBar.
- After a new record has been added, one cannot update that record to
the database even after the UpdateBatch method has been called, until
the Recordset is refreshed. This is the behaviour of Remote Data
Service, a Microsoft technology upon which RemoteDataBar and the DAO
components are built.
Contact
-------
Web site: http://www.businesscomponents.net/RemoteDataBar
General info: info@businesscomponents.net
Tech support: support@businesscomponents.net
OR: http://www.businesscomponents.net/RemoteDataBar/Feedback.asp